Skip to content

Conversation

@danielroe
Copy link
Member

@danielroe danielroe commented Sep 8, 2025

πŸ”— Linked issue

❓ Type of change

  • πŸ“– Documentation (updates to the documentation or readme)
  • 🐞 Bug fix (a non-breaking change that fixes an issue)
  • πŸ‘Œ Enhancement (improving an existing functionality)
  • ✨ New feature (a non-breaking change that adds functionality)
  • 🧹 Chore (updates to the build process or auxiliary tools and libraries)
  • ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

πŸ“š Description

this uses the new module dependencies feature in https://github.com/nuxt/nuxt/releases/tag/v4.1.0 to specify options for other modules (and require them).

Schema + kit are pinned because this repo is using shamefully-hoist, and the wrong version of each of these might be hoisted.

(We ultimately need to resolve that issue, but it's for another time.)

I'm opening this as a draft because it's very possible that something might break.

πŸ“ Checklist

  • I have linked an issue or discussion.
  • I have updated the documentation accordingly.

@github-actions github-actions bot added the v4 #4488 label Sep 8, 2025
@benjamincanac
Copy link
Member

@danielroe
Copy link
Member Author

danielroe commented Sep 8, 2025

oh, quite right. I'll update this PR once 4.1.2 is out.

@benjamincanac benjamincanac changed the title perf: use module dependencies to manipulate options perf(module): use moduleDependencies to manipulate options Sep 9, 2025
@benjamincanac benjamincanac force-pushed the v4 branch 2 times, most recently from 3f0c24a to c9ba808 Compare September 23, 2025 11:06
@pkg-pr-new
Copy link

pkg-pr-new bot commented Nov 3, 2025

npm i https://pkg.pr.new/@nuxt/ui@4927

commit: cc8fc95

@benjamincanac benjamincanac changed the title perf(module): use moduleDependencies to manipulate options feat(module)!: use moduleDependencies to manipulate options Nov 3, 2025
}

if ((hasNuxtModule('@nuxt/content') || options.content)) {
if (options.content || hasNuxtModule('@nuxt/content')) {
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've swapped these in every instance as checking options.content is always going to be more performant than calling hasNuxtModule

Co-authored-by: vercel[bot] <35613825+vercel[bot]@users.noreply.github.com>
Copy link
Member

@benjamincanac benjamincanac left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @danielroe ❀️

@benjamincanac benjamincanac merged commit f03f4c7 into v4 Nov 4, 2025
16 checks passed
@benjamincanac benjamincanac deleted the refactor/deps branch November 4, 2025 11:13
@benjamincanac benjamincanac restored the refactor/deps branch November 4, 2025 11:46
@jd-solanki
Copy link
Contributor

Hey @danielroe

Will this resolve the strict order issue for nuxt/content & nuxt/ui?

Do you want me to create issue for tracking auto creating main.css and including it in nuxt.config when creating new nuxt project and selecting Nuxt UI as module?

cc: @benjamincanac

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

v4 #4488

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants